LIBDRUM-985. Converted "load-etd-nightly" to Bash#262
Merged
dsteelma-umd merged 1 commit intodrum-mainfrom Aug 5, 2025
Merged
Conversation
Converted the "load-etd-nightly" script from C Shell to Bash (with the help of TerpAI). Removed the "count" variable, because it is no longer needed (it is a remnant of the MARC/CSV functionality of the script that was removed in earlier commits). https://umd-dit.atlassian.net/browse/LIBDRUM-985
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Converted the "load-etd-nightly" script from C Shell to Bash (with the help of TerpAI).
Removed the "count" variable, because it is no longer needed (it is a remnant of the MARC/CSV functionality of the script that was removed in earlier commits).
Also, If an argument specifying the directory to import from is not specified, the script exits with an exit code of 1 instead of 0. This is unlikely to occur in practice, and returning 1 is more correct from a Unix perspective (as not supplying an argument is an error).
https://umd-dit.atlassian.net/browse/LIBDRUM-985